I just fired up my KFLOP after installing Windows 10. I managed to get the drivers installed (I had to disable the digital signing mess in spite of downloading the latest drivers), and now I can't get the board to run. I get this error: "dsp_kflop.out date stamp doesn't match kflop firmware."

I go to the Kmotion config/flash screen and follow the directions over and over, and I turn the board on and off between tries, but no matter what I do, the firmware does not update. Also, I am getting "communication error" when I try "Recovery."

What's the deal?

BTW, I had to uninstall Kmotion432 and fix my desktop icons so they go to the 433 directory. They were still aimed at 432 after I installed the new software. Something the documentation does not warn about.

I can't get it to do "Recovery." After I turn the power back on, it says "timeout establishing bootloader connection."

Hi toolhorder,

Please be more specific on exactly what steps you are performing and exactly what is being reported.

What Version of drivers did you download?  The term "latest" can be confusing.  Our Released Version 4.33 doesn't contain signed drivers.

What Version of KMotion.exe are you running?

What DSPKFLOP.out file are you flashing?

What is the exact message you are getting?

We don't create any Desktop icons did you create them?

Regards

TK

 

I just fired up my KFLOP after installing Windows 10. I managed to get the drivers installed (I had to disable the digital signing mess in spite of downloading the latest drivers), and now I can't get the board to run. I get this error: "dsp_kflop.out date stamp doesn't match kflop firmware."

I go to the Kmotion config/flash screen and follow the directions over and over, and I turn the board on and off between tries, but no matter what I do, the firmware does not update. Also, I am getting "communication error" when I try "Recovery."

What's the deal?

BTW, I had to uninstall Kmotion432 and fix my desktop icons so they go to the 433 directory. They were still aimed at 432 after I installed the new software. Something the documentation does not warn about.

This is incredible. I clicked "Send," and Yahoo ate the message!

The version number is 433, and I am running Kmotion 4.33.

The DSKFLOP.out file is dated 12-1-15.

When I try "New Version," I get "unable to verify board type."

When I try "Recovery," I click the button, turn the board off, turn it on when prompted, and wait. It gives the timeout message I reported earlier.

When I try entering "reboot!" in the console, I get "Can't Connect to KMotion Board #0."

I clicked on what APPEARED to be a new version which was signed, but the number is 433. I must have misunderstood your site. I was only able to install it after disabling the signature check thing. The procedure was not quite consistent with what's on your site, but I figured it out.

The "About" screen says "Kmotion/Kflop 4.33".

The date on the dspkflop.out file is 12-1-15.

The messages are just as I typed them in this group.

I didn't know you don't create the icons. I must have done it when I installed the software originally.

For "Recovery," I'm clicking the button, turning off the board, and turning it back on when the software tells me too. It times out.

When I click "New Version," I get, "Unable to verify board type."

Windows 10 seems to think the board is unfriendly. In the "properties" area in Device Manager, it says, "Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)."

There is a yellow triangle over the little KFlop icon.

Hi toolhoarder,

That would indicate the signed drivers haven't been loaded and driver signing enforcement hasn't been turned off.

Sorry for the confusion. V4.33 doesn't have signed rivers.  They are located in the link below it labeled:
Digitally Signed USB Drivers for KFLOP now available here New*

Regards

TK

 

Windows 10 seems to think the board is unfriendly. In the "properties" area in Device Manager, it says, "Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)."

There is a yellow triangle over the little KFlop icon.

Okay, I finally noticed the 4.34 driver link and installed it. Things are a little less crazy, but it still times out when I try to do "Recovery," and it says "unable to verify board type" when I try to do "New Version."

What steps are you doing exactly for the Recovery and exactly what happens?  Do you have KFLOP checked under the menu options? If it the code runs and communicates are you immediately Flashing New Version before cycling power?

Regards

TK

 

Okay, I finally noticed the 4.34 driver link and installed it. Things are a little less crazy, but it still times out when I try to do "Recovery," and it says "unable to verify board type" when I try to do "New Version."

Here is what the console says:

Fri, Jul 01, 2016, 06:00:57  KMotion Program Started
ProgFlashImage
Program Flash Image Complete
Verify Complete
KFLOP 4.32
Ready

Let's see.

Kflop is checked.

To do recovery:

1. Click the Recovery button.
2. Click "OK" on the window that comes up.
3. Click "Open" on the next window that comes up, selecting the DSK whatever file.
4. Turn off Kflop power, in response to next window.
5. Click "OK."
6. Turn Kflop on at prompt.
7. Wait for green progress line to fill.
8. Receive "Timeout establishing bootloader" etc.

When I first start Kmotion, I get "Kflop present but not responding."

Here is what the console says.

Fri, Jul 01, 2016, 06:00:57  KMotion Program Started
ProgFlashImage
Program Flash Image Complete
Verify Complete
KFLOP 4.32
Ready

Well, this is embarrassing.

It had been so long since I had turned the machine on, I forgot that the KFlop was powered by USB, not the main switch. I thought I was powering the KFlop down, but I was actually just powering the KStep down.

Heh heh. Never mind.